Policy enforcement across wireless communication networks over application functions

ABSTRACT

A wireless communication network delivers policy enforcement to a wireless user device in another wireless communication network. The wireless communication network wirelessly serves the wireless user device based on a policy. The wireless communication network determines when the wireless user device is visiting the other wireless communication network, and in response, selects the policy for the wireless user device. The wireless communication network transfers the selected policy for the wireless user device to the other wireless communication network. The other wireless communication network receives and enforces the selected policy for the wireless user device.

RELATED CASES

This United States patent application is a continuation of U.S. patentapplication Ser. No. 17/220,532 that was filed on Apr. 1, 2021 and isentitled “POLICY ENFORCEMENT ACROSS WIRELESS COMMUNICATION NETWORKS OVERAPPLICATION FUNCTIONS.” U.S. patent application Ser. No. 17/220,532 ishereby incorporated by reference into this United States patentapplication.

TECHNICAL BACKGROUND

Wireless communication networks provide wireless data services towireless user devices. Exemplary wireless data services includemachine-control, internet-access, media-streaming, andsocial-networking. Exemplary wireless user devices comprise phones,computers, vehicles, robots, and sensors. The wireless communicationnetworks have Radio Access Networks (RANs) which exchange wirelesssignals with the wireless user devices over radio frequency bands. Thewireless signals use wireless network protocols like Fifth GenerationNew Radio (5GNR), Long Term Evolution (LTE), Institute of Electrical andElectronic Engineers (IEEE) 802.11 (WIFI), and Low-Power Wide AreaNetwork (LP-WAN). The RANs exchange network signaling and user data withnetwork elements that are often clustered together into wireless networkcores. The RANs are connected to the wireless network cores overbackhaul data links.

The RANs comprise Radio Units (RUs), Distributed Units (DUs) andCentralized Units (CUs). The RUs are mounted at elevation and haveantennas, modulators, signal processor, and the like. The RUs areconnected to the DUs which are usually nearby network computers. The DUshandle lower wireless network layers like the Physical Layer (PHY) andMedia Access Control (MAC). The DUs are connected to the CUs which arelarger computer centers that are closer to the network cores. The CUshandle higher wireless network layers like the Radio Resource Control(RRC) and Packet Data Convergence Protocol (PDCP). The CUs are coupledto network functions in the network cores. The network cores execute thenetwork functions to provide wireless data services to the wireless userdevices over the RANs. Exemplary network functions include Access andMobility Management Functions (AMFs), Policy Control Functions (PCFs),and Application Functions (AFs).

A visiting wireless user device attaches to a wireless communicationnetwork over a RAN. A visiting UE is attached to a visited wirelesscommunication network that is not its home wireless communicationnetwork. In the visited wireless communication network, a visited AMFqueries a visited PCF for service rules for the visiting wireless userdevice. The visited PCF selects wireless service rules for the visitingwireless user device based on a roaming agreement between the visitedwireless communication network and the home wireless communicationnetwork of the visiting wireless user device. Unfortunately, the PCFsineffectively share policy data with one another. Moreover, the homePCFs ineffectively control the wireless service rules in the visitedPCFs.

TECHNICAL OVERVIEW

A wireless communication network delivers policy enforcement to awireless user device in another wireless communication network. Thewireless communication network wirelessly serves the wireless userdevice based on a policy. The wireless communication network determineswhen the wireless user device is visiting the other wirelesscommunication network, and in response, selects the policy for thewireless user device. The wireless communication network transfers theselected policy for the wireless user device to the other wirelesscommunication network. The other wireless communication network receivesand enforces the selected policy for the wireless user device.

DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a wireless communication network to enforce userpolicies across wireless communication networks.

FIG. 2 illustrates an exemplary operation of the wireless communicationnetwork to enforce user policies across wireless communication networks.

FIG. 3 illustrates another exemplary operation of the wirelesscommunication network to enforce user policies across wirelesscommunication networks.

FIG. 4 illustrates a Fifth Generation (5G) communication network toenforce user policies across wireless communication networks.

FIG. 5 illustrates the 5G UEs in the 5G communication networks.

FIG. 6 illustrates 5G RANs in the 5G communication networks.

FIG. 7 illustrates Network Function Virtualization Infrastructure(NFVIs) in the 5G communication networks.

FIG. 8 further illustrates the NFVIs in the 5G communication networks.

FIG. 9 illustrates an exemplary operation of the 5G communicationnetwork to enforce user policies across wireless communication networks.

DETAILED DESCRIPTION

FIG. 1 illustrates wireless communication network 100 to enforce userpolicies across wireless communication networks. Wireless communicationnetwork 100 delivers services to UE 101 like internet-access, machinecommunications, media-streaming, or some other wireless communicationsproduct. Wireless communication network 100 comprises UE 101, RadioAccess Network (RAN) 111, Network Function (NF) 121, Policy ControlFunction (PCF) 122, and Application Function (AF) 123. Other wirelesscommunication network 130 comprises UE 131, other RAN 141, other NF 151,other PCF 152, and other AF 153.

Various examples of network operation and configuration are describedherein. In some examples, AF 123 receives a user policy from other AF153 in other wireless communication network 130. Other AF 153 receivedthe user policy from other PCF 152 in other wireless communicationnetwork 130. AF 123 transfers the user policy to PCF 122. PCF 122distributes the user policy to NF 121. NF 121 enforces the user policy.PCF 122 identifies another user policy. PCF 122 transfers the other userpolicy to AF 123. AF 123 receives the other user policy from the PCF 122and responsively transfers the other user policy to other AF 153. OtherAF 153 transfers the other user policy to other PCF 152. Other PCF 152responsively distributes the other user policy to other NF 151. Other NF151 enforces the other user policy. Advantageously, PCF 122 effectivelyshares policy data with PCF 152. Moreover, the PCF 122 effectivelycontrols the wireless service rules in PCF 152 when the two PCFs residein different wireless communication networks.

UE 101, UE 131, RAN 111, and RAN 141 communicate over links usingwireless technologies like Fifth Generation New Radio (5GNR), Long TermEvolution (LTE), Low-Power Wide Area Network (LP-WAN), Institute ofElectrical and Electronic Engineers (IEEE) 802.11 (WIFI), Bluetooth,and/or some other type of wireless networking protocol. The wirelesstechnologies use electromagnetic frequencies in the low-band, mid-band,high-band, or some other portion of the electromagnetic spectrum. RAN111, RAN 141, network functions 121-123, and network functions 151-153communicate over various links that use metallic links, glass fibers,radio channels, or some other communication media. The links use FifthGeneration Core (5GC), IEEE 802.3 (Ethernet), Time Division Multiplex(TDM), Data Over Cable System Interface Specification (DOCSIS), InternetProtocol (IP), General Packet Radio Service Transfer Protocol (GTP),5GNR, LTE, WIFI, virtual switching, inter-processor communication, businterfaces, and/or some other data communication protocols.

UE 101 and UE 131 comprise computers, phones, vehicles, sensors, robots,other types of data appliances with wireless and/or wirelinecommunication circuitry. RAN 111 and RAN 141 are depicted as towers butRAN 111 and RAN 141 may use other mounting structures or no mountingstructure at all. RAN 111 and RAN 141 may comprise Fifth Generation (5G)RANs, LTE RANs, gNodeBs, eNodeBs, NB-IoT access nodes, LP-WAN basestations, wireless relays, WIFI hotspots, ENET access nodes, Bluetoothaccess nodes, and/or other wireless or wireline network transceivers. UE101, UE 131, RAN 111, and RAN 141 comprise antennas, amplifiers,filters, modulation, analog/digital interfaces, microprocessors,software, memories, transceivers, bus circuitry, and the like. NF 121and other NF 151 comprise network functions like Access and MobilityManagement functions (AMFs), Session Management Functions (SMFs), andthe like. RAN 111, RAN 141, network functions 121-123, and networkfunctions 151-153 comprise microprocessors, software, memories,transceivers, bus circuitry, and the like. The microprocessors compriseDigital Signal Processors (DSP), Central Processing Units (CPU),Graphical Processing Units (GPU), Application-Specific IntegratedCircuits (ASIC), and/or the like. The memories comprise Random AccessMemory (RAM), flash circuitry, disk drives, and/or the like. Thememories store software like operating systems, user applications, radioapplications, and network functions. The microprocessors retrieve thesoftware from the memories and execute the software to drive theoperation of wireless communication network 100 as described herein.

FIG. 2 illustrates an exemplary operation of wireless communicationnetwork 100 to enforce user policies across wireless communicationnetworks. The operation may vary in other examples. AF 123 receives auser policy from other AF 153 in other wireless communication network130. Other AF 130 received the user policy from other PCF 152 (201). AF123 transfers the user policy to PCF 122 (202). PCF 122 receives theuser policy from AF 123 (203). PCF 122 distributes the user policy to NF121 (204). NF 121 enforces the user policy (205). For example, the userpolicy may comprise a time-of-day usage rule for UE 101 and NF 121 mayenforce the time-of-day usage rule for UE 101. PCF 122 identifiesanother user policy (206). PCF 122 transfers the other user policy to AF123 (207). AF 123 receives the other user policy from PCF 122 (208). AF123 responsively transfers the other user policy to other AF 153. OtherAF 153 transfers the other user policy to other PCF 152. Other PCF 152distributes the other user policy to other NF 153. Other NF 153 enforcesthe other user policy (209).

FIG. 3 illustrates an exemplary operation of wireless communicationnetwork 100 to enforce user policies across wireless communicationnetworks. The operation may vary in other examples. Other PCF 152identifies a user policy for UE 101. For example, UE 101 may be visitingon wireless communication network 100 and other PCF 152 may identify auser policy for UE 101 based on the roaming agreement between thenetworks. Other PCF 152 transfers the user policy for UE 101 to other AF153. Other AF 153 transfers the user policy for UE 101 to AF 123. AF 123responsively transfers the user policy for UE 101 to PCF 122. PCF 122approves the user policy for UE 101 and distributes the user policy toNF 121. NF 121 enforces the user policy for UE 101. For example, thepolicy may indicate authorized services for UE 101 and NF 121 may serveUE 101 with the authorized services and withhold unauthorized servicesfrom UE 101. In some examples, the user policy indicates a LocalBreakout (LBO) rule for wireless communication networks 100 and 130.

PCF 122 identifies another user policy for UE 131. For example, UE 131'shome network may be wireless communication network 100 and PCF 122 mayreceive indication that UE 131 is visiting on other wirelesscommunication network 130. PCF 122 transfers the other user policy forUE 131 to AF 123. AF 123 transfers the other user policy for UE 131 toother AF 153. Other AF 153 transfers the other user policy for UE 131 toother PCF 152. Other PCF 152 approves the other user policy for UE 131and distributes the other user policy to other NF 151. Other NF 151enforces the other user policy for UE 131. In some examples, the userpolicies comprise default visiting policies for UEs 101 and 131. In someexamples, the user policies comprise customized visiting policies forUEs 101 and 131. For example, the user policy for UE 101 may indicate aspecific slice type for UE 101.

FIG. 4 illustrates Fifth Generation (5G) communication network 400 toenforce user policies across wireless communication networks. 5Gcommunication network 400 comprises an example of wireless communicationnetwork 100, although network 100 may differ. Other 5G communicationnetwork 430 comprises an example of other wireless communication network130, although network 130 may differ. 5G communication network 400comprises 5G UE 401, 5G RAN 410, and 5G network core 420. 5G UE 401comprises a visiting UE from other 5G communication network 430 that isvisiting on home 5G communication network 400. 5G RAN 410 comprises 5GRadio Unit (RU) 411, 5G Distributed Unit (DU) 412, and 5G CentralizedUnit (CU) 413. 5G network core 420 comprises Access and MobilityManagement Function (AMF) 421, Session Management Function (SMF) 422,User Plane Function (UPF) 423, Unified Data Management (UDM) 424, PolicyControl Function (PCF) 425, and Application Function (AF) 426. Other 5Gcommunication network 430 comprises 5G UE 431, 5G RAN 440, and 5Gnetwork core 450. 5G UE 431 comprises a visiting UE from 5Gcommunication network 400 that is visiting on other 5G communicationnetwork 430. 5G RAN 440 comprises 5G RU 441, 5G DU 442, and 5G CU 443.Other 5G network core 450 comprises other Access and Mobility ManagementFunction (oAMF) 451, other Session Management Function (oSMF) 452, otherUser Plane Function (oUPF) 453, other Unified Data Management (oUDM)454, other Policy Control Function (oPCF) 455, and other ApplicationFunction (oAF) 456. Other network functions and network elements aretypically present in network cores 420 and 450 but are omitted forclarity.

UE 401 wirelessly attaches to RU 411 and transfers attachment signalingto CU 413 over RU 411 and DU 412. The attachment signaling indicates ahome Public Land Mobile Network (PLMN) ID for other 5G communicationnetwork 430 and a Subscription Concealed Identifier (SUCI) for UE 401.The PLMN ID indicates other 5G communications network 430 as the homenetwork for UE 401. The SUCI is a privacy preserving identifier for UE401 that conceals a Subscriber Permanent Identifier (SUPI) for UE 401.CU 413 transfers a registration request for UE 401 that indicates thePLMN ID and SUCI of UE 401 to AMF 421. AMF 421 interacts with othernetwork functions to authenticate and authorize UE 401 for visiting dataservices. Responsive to the authentication and authorization, AMF 421requests UE context for UE 401 from UDM 424. UDM 424 transfers defaultUE context for UE 401 to AMF 421 based on the roaming agreement between5G communication network 400 and other 5G communication network 430. TheUE context comprises default Quality-of-Service (QoS) metrics, defaultslice identifiers, and default network addresses in accordance with theroaming agreement. AMF 421 transfers the default UE context for UE 401to CU 413. CU 413 transfers the default UE context to UE 401 over DU 412and RU 411.

UE 401 wirelessly transfers a Protocol Data Unit (PDU) session requestto CU 413 over RU 411 and DU 412. CU 413 transfers the PDU sessionrequest to AMF 421. AMF 421 queries PCF 425 for policy rules to supportthe PDU session requested by UE 401. PCF 425 drives AF 426 to retrieveservice policies for UE 401 from other 5G communication network 430. AF426 transfers a visiting service request that indicates the SUCI for UE401 to oAF 456. oAF 456 notifies oPCF 455 of the service request. oPCF455 identifies UE 401 based on the SUCI and interacts with oUDM 454 toretrieve the subscription profile for UE 401. The subscription profileindicates authorized services for UE 401. For example, the subscriptionprofile may specify that UE 401 can use low-latency slice types. oUDM454 transfers the subscription profile to oPCF 455. oPCF 455 indicatesthe authorized services for UE 401 to oAF 456.

oAF 456 receives the indication from oPCF 455. oAF 456 generates apolicy template for UE 401. The policy template indicates the authorizedservices for UE 401 and is associated with the SUCI of UE 401 to concealthe identify of UE 401. For example, the policy template may indicateauthorized slice types, an authorized QoS range, an authorized bit raterange, authorized times/locations, Local Breakout (LBO) rules, and otheravailable services for UE 401. oAF 456 transfers the policy template forUE 401 to AF 426. AF 426 receives and processes the policy template andresponsively generates a user policy for UE 401. The user policycomprises selected service values for UE 401 derived from the policytemplate. For example, AF 426 may identify that UE 401 is authorized touse guaranteed bit rate services and may generate a user policy thatincludes guaranteed bit rate services. AF 426 transfers the proposeduser policy for UE 401 to oAF 456. oAF 456 transfers the user policy tooPCF 455. oPCF 455 processes the user policy and responsively approvesthe user policy for UE 401. For example, oPCF 455 may determine that theslice type and QoS level in the user policy for UE 401 are authorized bythe subscription profile of UE 401. oPCF 455 transfers a policy approvalto oAF 456 and oAF 456 forwards the policy approval to AF 426.

In response to the policy approval, AF 426 transfers the user policy forUE 401 to PCF 425. PCF 425 interacts with UDM 424 to update the UEcontext for UE 401 to enforce the user policy. For example, UDM 424 mayupdate the QoS level for UE 401 in response to the interaction with PCF425. PCF 425 approves the PDU session for UE 401 and directs AMF 421 toimplement the user policy for UE 401. In response, AMF 421 retrieves theupdated UE context for UE 401 from UDM 424. AMF 421 indicates theupdated UE context for UE 401 to SMF 422 and directs SMF 422 toestablish the PDU session for UE 401. SMF 422 selects UPF 423 to servethe PDU session to UE 401 based on the updated UE context. SMF 422transfers session context to AMF 421. AMF 421 transfers the sessioncontext for the PDU session to CU 413. CU 413 transfers the sessioncontext to UE 401 over DU 412 and RU 411. UE 401 uses the sessioncontext to exchange user data for the PDU session with 5G network core420. UE 401 exchanges user data for the PDU session with CU 413 over RU411 and DU 412. CU 413 exchanges the user data for the PDU session withUPF 423. UPF 423 exchanges the user data for the PDU session withexternal networks.

AF 426 receives a visiting service request from oAF 456 that indicatesthe SUCI for UE 431. AF 426 identifies UE 431 based on the SUCI andnotifies PCF 425 of the service request. PCF 425 interacts with UDM 424to retrieve the subscription profile for UE 431. UDM 424 transfers thesubscription profile to PCF 425. PCF 425 indicates the authorizedservices for UE 431 to AF 426. AF 426 receives the indication from PCF425 and responsively generates a policy template for UE 431 thatindicates authorized services for UE 431. AF 426 transfers the policytemplate for UE 431 to oAF 456. oAF 456 receives and processes thepolicy template and responsively generates a user policy that comprisesselected service values based on the policy template for UE 401. oAF 456transfers the proposed user policy for UE 431 to AF 426. AF 426transfers the user policy to PCF 425. PCF 425 processes the user policyand responsively approves the user policy for UE 431. For example, PCF425 may determine that the selected slice type for UE 431 is authorizedby the subscription profile of UE 401. PCF 425 transfers a policyapproval to AF 426. AF 426 transfers the policy approval to oAF 456.

In response to the policy approval, oAF 456 transfers the user policyfor UE 431 to oPCF 455. oPCF 455 interacts with oUDM 454 and oAMF 451 todistribute the user policy for UE 431. oUDM 454 updates the UE contextfor UE 431 to enforce the user policy. oPCF 455 transfers a PDU sessionapproval for UE 431 to oAMF 451. In response, oAMF 451 retrieves theupdated UE context for UE 431 from oUDM 454. oAMF 451 directs oSMF 452to establish the PDU session for UE 431 using the updated UE context.oSMF 452 selects oUPF 453 to serve the PDU session to UE 431 based onthe updated UE context. oSMF 452 transfers session context to oAMF 451and oAMF 451 transfers the session context for the PDU session to UE 431over RAN 440. UE 431 exchanges user data for the PDU session with CU 443over RU 441 and DU 442. CU 443 exchanges the user data for the PDUsession with oUPF 453. oUPF 453 exchanges the user data for the PDUsession with external networks.

In some examples, PCF 425 may transfer user policy audit requests tooPCF 455 to determine service metrics for UE 431. PCF 425 generates anaudit request to retrieve the policy template for UE 431. PCF 425transfers the audit request to AF 426. AF 426 transfers the auditrequest to oAF 456 and indicates the SUCI for UE 431. oAF 456 processesthe SUCI for UE 431 and responsively identifies the policy template forUE 431. oAF 456 transfers the policy template for UE 431 to AF 426 andAF 426 forwards the policy template to PCF 425. PCF processes the usertemplate and determines if the policy template values are sufficient forUE 431. For example, PCF 424 may determine if the policy templateindicates authorized slice types, an authorized QoS range, an authorizedbit rate range, authorized times/locations, and other service metricsfor UE 431. In some examples, AF 426 receives audit requests from oAF456 for the policy template for UE 401. AF 426 uses the SUCI for UE 401to identify the policy template for UE 401 and transfers the policytemplate to oAF 456. oAF 456 transfers the policy template to oPCF 455.In a similar manner as PCF 425, oPCF 455 processes the user template forUE 401 to determine if the template values are sufficient.

FIG. 5 illustrates 5G UEs 401 and 431 that are served PDU sessions basedon visiting user policies. UE 401 comprises an example of UE 101,although UE 101 may differ. UE 431 comprises an example of UE 131,although UE 131 may differ. UEs 401 and UE 431 comprise 5G radio 501 anduser circuitry 502. Radio 501 comprises antennas, amplifiers, filters,modulation, analog-to-digital interfaces, Digital Signal Processers(DSP), memory, and transceivers that are coupled over bus circuitry.User circuitry 502 comprises memory, CPU, user interfaces andcomponents, and transceivers that are coupled over bus circuitry. Thememory in user circuitry 502 stores an operating system (OS), userapplications (USER), and 5GNR network applications for Physical Layer(PHY), Media Access Control (MAC), Radio Link Control (RLC), Packet DataConvergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP),and Radio Resource Control (RRC). The antenna in radio 501 is wirelesslycoupled to 5G RAN 510 over a 5GNR link. A transceiver in radio 501 iscoupled to a transceiver in user circuitry 502. A transceiver in usercircuitry 502 is typically coupled to the user interfaces and componentslike displays, controllers, and memory.

In radio 501, the antennas receive wireless signals from 5G RANs 410 and440 that transport downlink 5GNR signaling and data. The antennastransfer corresponding electrical signals through duplexers to theamplifiers. The amplifiers boost the received signals for filters whichattenuate unwanted energy. Demodulators down-convert the amplifiedsignals from their carrier frequency. The analog/digital interfacesconvert the demodulated analog signals into digital signals for theDSPs. The DSPs transfer corresponding 5GNR symbols to user circuitry 502over the transceivers. In user circuitry 502, the CPU executes thenetwork applications to process the 5GNR symbols and recover thedownlink 5GNR signaling and data. The 5GNR network applications receivenew uplink signaling and data from the user applications. The networkapplications process the uplink user signaling and the downlink 5GNRsignaling to generate new downlink user signaling and new uplink 5GNRsignaling. The network applications transfer the new downlink usersignaling and data to the user applications. The 5GNR networkapplications process the new uplink 5GNR signaling and user data togenerate corresponding uplink 5GNR symbols that carry the uplink 5GNRsignaling and data.

In radio 501, the DSP processes the uplink 5GNR symbols to generatecorresponding digital signals for the analog-to-digital interfaces. Theanalog-to-digital interfaces convert the digital uplink signals intoanalog uplink signals for modulation. Modulation up-converts the uplinkanalog signals to their carrier frequency. The amplifiers boost themodulated uplink signals for the filters which attenuate unwantedout-of-band energy. The filters transfer the filtered uplink signalsthrough duplexers to the antennas. The electrical uplink signals drivethe antennas to emit corresponding wireless 5GNR signals to 5G RANs 410and 440 that transport the uplink 5GNR signaling and data.

RRC functions comprise authentication, security, handover control,status reporting, QoS, network broadcasts and pages, and networkselection. SDAP functions comprise QoS marking and flow control. PDCPfunctions comprise security ciphering, header compression anddecompression, sequence numbering and re-sequencing, de-duplication. RLCfunctions comprise Automatic Repeat Request (ARQ), sequence numberingand resequencing, segmentation and resegmentation. MAC functionscomprise buffer status, power control, channel quality, Hybrid ARQ(HARQ), user identification, random access, user scheduling, and QoS.PHY functions comprise packet formation/deformation,windowing/de-windowing, guard-insertion/guard-deletion,parsing/de-parsing, control insertion/removal,interleaving/de-interleaving, Forward Error Correction (FEC)encoding/decoding, channel coding/decoding, channelestimation/equalization, and rate matching/de-matching,scrambling/descrambling, modulation mapping/de-mapping, layermapping/de-mapping, precoding, Resource Element (RE) mapping/de-mapping,Fast Fourier Transforms (FFTs)/Inverse FFTs (IFFTs), and DiscreteFourier Transforms (DFTs)/Inverse DFTs (IDFTs).

FIG. 6 illustrates 5G RUs 411 and 441, 5G DUs 412 and 442, and 5G CUs413 and 443 that serve PDU based on visiting user policies. RU 411, DU412, and CU 413 comprise an example of RAN 111, although RAN 111 maydiffer. RU 441, DU 442, and CU 443 comprise an example of RAN 141,although RAN 141 may differ. RUs 411 and 441 comprises antennas,amplifiers, filters, modulation, analog-to-digital interfaces, DSP,memory, and transceivers (XCVRs) that are coupled over bus circuitry. UE401 is wirelessly coupled to the antennas in RU 411 over 5GNR links. UE431 is wirelessly coupled to antennas in RU 441 over 5GNR links.Transceivers in 5G RU 411 are coupled to transceivers in 5G DU 412 andtransceivers in 5G RU 441 are coupled to transceivers in 5G RU 442 overfronthaul links like enhanced Common Public Radio Interface (eCPRI). TheDSPs in RUs 411 and 441 execute their operating systems and radioapplications to exchange 5GNR signals with UEs 401 and 431 and toexchange 5GNR data units with DUs 412 and 442.

For the uplink, the antennas receive wireless signals from UEs 401 and431 that transport uplink 5GNR signaling and data. The antennas transfercorresponding electrical signals through duplexers to the amplifiers.The amplifiers boost the received signals for filters which attenuateunwanted energy. Demodulators down-convert the amplified signals fromtheir carrier frequencies. The analog/digital interfaces convert thedemodulated analog signals into digital signals for the DSPs. The DSPstransfer corresponding 5GNR symbols to DUs 412 and 442 over thetransceivers.

For the downlink, the DSPs receive downlink 5GNR symbols from DUs 412and 442. The DSPs process the downlink 5GNR symbols to generatecorresponding digital signals for the analog-to-digital interfaces. Theanalog-to-digital interfaces convert the digital signals into analogsignals for modulation. Modulation up-converts the analog signals totheir carrier frequencies. The amplifiers boost the modulated signalsfor the filters which attenuate unwanted out-of-band energy. The filterstransfer the filtered electrical signals through duplexers to theantennas. The filtered electrical signals drive the antennas to emitcorresponding wireless signals to 5G UEs 401 and 431 that transport thedownlink 5GNR signaling and data.

DUs 412 and 442 comprises memory, CPU, and transceivers that are coupledover bus circuitry. The memory in 5G DUs 412 and 442 stores operatingsystems and 5GNR network applications like PHY, MAC, and RLC. CUs 413and 443 comprise memory, CPU, and transceivers that are coupled over buscircuitry. The memory in CUs 413 and 443 store an operating system and5GNR network applications like PDCP, SDAP, and RRC. Transceivers in 5GDUs 412 and 442 are coupled to transceivers in RUs 411 and 441 overfront-haul links. Transceiver in DUs 412 and 442 are coupled totransceivers in CUs 413 and 443 over mid-haul links. A transceiver in CU413 is coupled to network core 420 over backhaul links. A transceiver inCU 443 is coupled to other network core 450 over backhaul links.

RLC functions comprise ARQ, sequence numbering and resequencing,segmentation and resegmentation. MAC functions comprise buffer status,power control, channel quality, HARQ, user identification, randomaccess, user scheduling, and QoS. PHY functions comprise packetformation/deformation, guard-insertion/guard-deletion,parsing/de-parsing, control insertion/removal,interleaving/de-interleaving, FEC encoding/decoding, channelcoding/decoding, channel estimation/equalization, and ratematching/de-matching, scrambling/descrambling, modulationmapping/de-mapping, layer mapping/de-mapping, precoding, REmapping/de-mapping, FFTs/IFFTs, and DFTs/IDFTs. PDCP functions includesecurity ciphering, header compression and decompression, sequencenumbering and re-sequencing, de-duplication. SDAP functions include QoSmarking and flow control. RRC functions include authentication,security, handover control, status reporting, QoS, network broadcastsand pages, and network selection.

FIG. 7 illustrates Network Function Virtualization Infrastructure (NFVI)700 and other NFVI 710. NFVI 700 comprises an example of networkfunctions 121-123, although functions 121-123 may vary from thisexample. Other NFVI 710 comprises an example of network functions151-153, although functions 151-153 may vary from this example. NFVI 700comprises NFVI hardware 701, NFVI hardware drivers 702, NFVI operatingsystems 703, NFVI virtual layer 704, and NFVI Virtual Network Functions(VNFs) 705. NFVI hardware 701 comprises Network Interface Cards (NICs),CPU, RAM, Flash/Disk Drives (DRIVE), and Data Switches (SW). NFVIhardware drivers 702 comprise software that is resident in the NIC, CPU,RAM, DRIVE, and SW. NFVI operating systems 703 comprise kernels,modules, applications, containers, hypervisors, and the like. NFVIvirtual layer 704 comprises vNIC, vCPU, vRAM, vDRIVE, and vSW. NFVI VNFs705 comprise AMF 721, SMF 722, UPF 723, UDM 724, PCF 725, and AF 726.Additional VNFs and network elements like Authentication Server Function(AUSF), Network Slice Selection Function (NSSF), Unified Data Registry(UDR), and Network Exposure Function (NEF) are typically present but areomitted for clarity. NFVI 700 may be located at a single site or bedistributed across multiple geographic locations. The NIC in NFVIhardware 701 is coupled to 5G RAN 410, to a NIC in NFVI hardware 711,and to external systems. NFVI hardware 701 executes NFVI hardwaredrivers 702, NFVI operating systems 703, NFVI virtual layer 704, andNFVI VNFs 705 to form AMF 421, SMF 422, UPF 423, UDM 424, PCF 425, andAF 426.

In a like manner, other NFVI 710 comprises NFVI hardware 711, NFVIhardware drivers 712, NFVI operating systems 713, NFVI virtual layer714, and NFVI VNFs 715. NFVI hardware 711 comprises NICs, CPU, RAM,DRIVE, and SW. NFVI hardware drivers 712 comprise software that isresident in the NIC, CPU, RAM, DRIVE, and SW. NFVI operating systems 713comprise kernels, modules, applications, containers, hypervisors, andthe like. NFVI virtual layer 714 comprises vNIC, vCPU, vRAM, vDRIVE, andvSW. NFVI VNFs 705 comprise oAMF 751, oSMF 752, oUPF 753, oUDM 754, oPCF755, and oAF 756. Additional VNFs and network elements are typicallypresent but are omitted for clarity. Other NFVI 710 may be located at asingle site or be distributed across multiple geographic locations. TheNIC in NFVI hardware 711 is coupled to 5G RAN 440, to a NIC in NFVIhardware 701, and to external systems. NFVI hardware 711 executes NFVIhardware drivers 712, NFVI operating systems 713, NFVI virtual layer714, and NFVI VNFs 715 to form oAMF 451, oSMF 452, oU5F 423, oUDM 454,oPCF 455, and oAF 456.

FIG. 8 further illustrates NFVI 700 and other NFVI 710 in 5Gcommunication networks 400 and 430. AMF 421 performs UE registration andconnection, UE connection/mobility management, and UE authentication andauthorization, SMF 422 performs session establishment and management,UPF selection and control, network address allocation, and N1termination. UPF 423 performs packet routing & forwarding, packetinspection, QoS handling, PDU interconnection, and mobility anchoring,UDM 424 performs UE context management, UE subscription management, andDNN data modification, PCF 425 performs network rules management,visiting policy approval, and visiting policy distribution. INF 426performs network core service support, visiting network interfacing, andvisiting policy generation. In a like manner, other NFs 451-456 performsimilar functions to NFs 421-426.

In this example, 5G communication network 400 enforces a user policy fora QoS level for UE 401 and directs 5G communication network 430 toenforce a user policy for a QoS level and LBO rule for UE 431, howeverthe user policies may differ in other examples. AMF 421 receives a PDUsession request from UE 401. AMF 421 interacts with PCF 425 to determineif the PDU session requested by UE 401 is supported. In response, PCF425 directs AF 426 to retrieve service policies for UE 401 from other 5Gcommunication network 430. AF 426 transfers a visiting service requestthat indicates SUCI of UE 401 to oAF 456. oAF 456 identifies UE 401based on the SUCI and transfers the service request to oPCF 455. oPCF455 retrieves the subscription profile for UE 401 from oUDM 454. oPCF455 determines that UE 401 is authorized for a range of QoS levels andindicates the authorized QoS range for UE 401 to oAF 456.

oAF 456 receives the indication and generates a policy template for UE401 that indicates the range of QoS levels for UE 401. For example, oAF456 may update the template to include the range of QoS levels for UE401 while leaving other template values (e.g., slice type) at defaults.oAF 456 transfers the policy template for UE 401 to AF 426. AF 426responsively generates a user policy for UE 401 that includes a QoSlevel within the authorized range. AF 426 transfers the proposed userpolicy for UE 401 to oPCF 455 over oAF 456. oPCF 455 approves the userpolicy for the QoS level for UE 401. oPCF 455 transfers a policyapproval to AF 426 over oAF 456.

In response to the policy approval, AF 426 transfers the user policy forthe QoS level for UE 401 to PCF 425. PCF 425 directs UDM 424 to updatethe UE context for UE 401 to include the QoS level. PCF 425 approves thePDU session for UE 401 and directs AMF 421 to enforce the user policyfor the QoS level for UE 401. AMF 421 retrieves the updated UE contextfor UE 401 from UDM 424. AMF 421 directs SMF 422 to establish the PDUsession for UE 401 using the updated QoS level. SMF 422 selects UPF 423to serve the PDU session to UE 401 at the updated QoS level. SMF 422transfers session context to AMF 421 that indicates UPF 423. AMF 421transfers the session context for the PDU session to UE 401 over RAN410. UPF 423 exchanges user data for the PDU session with UE 401 overRAN 410 at the QoS level. UPF 423 exchanges the user data for the PDUsession with external networks.

AF 426 receives a visiting service request for UE 431 from oAF 456. Theservice request indicates the SUCI for UE 431 and that UE 431 requesteda PDU session over other 5G communication network 430. AF 426 uses theSUCI to identify UE 431 and notifies PCF 425 of the service request forUE 431. PCF 425 retrieves subscription information for UE 431 from UDM424. PCF 425 determines a range of QoS levels that UE 431 is authorizedfor and determines an LBO rule for UE 431. PCF 425 indicates the rangeof QoS levels and LBO rule for UE 431 to AF 426. AF 426 receives theindication from PCF 425. AF 426 generates a policy template for UE 431that indicates the range of QoS levels and LBO rule for UE 431 andindicates default values for other template values. AF 426 transfers thepolicy template for UE 431 to oAF 456. oAF 456 processes the policytemplate and responsively generates a user policy that comprises a QoSlevel within the indicated range and that implements the LBO rule. oAF456 transfers the proposed user policy to PCF 425 over AF 426. PCF 425approves the user policy for the QoS level and LBO rule for UE 431. PCF425 transfers a policy approval to oAF 456 over AF 426.

oAF 456 transfers the user policy for UE 431 to oPCF 455. oPCF 455distributes the user policy for UE 431 to oUDM 454 and oAMF 451. oUDM454 updates the UE context for UE 431 to include the QoS level and LBOrule. oPCF 455 approves a PDU session request from oAMF 451 for UE 431.In response, oAMF 451 retrieves the updated UE context for UE 431 fromoUDM 454. oAMF 451 directs oSMF 452 to establish the PDU session for UE431 at the updated QoS level and to implement the LBO rule for UE 431.oSMF 452 selects oUPF 453 to serve the PDU session to UE 431 at theupdated QoS level. oSMF 452 transfers session context to oAMF 451. oAMF451 transfers the session context for the PDU session to UE 431 over RAN440. oUPF 453 exchanges user data for the PDU session with UE 431 overRAN 440 at the updated QoS level. oUPF 453 exchanges the user data forthe PDU session with external networks.

FIG. 9 illustrates an exemplary operation of 5G communication network400 to enforce user policies across wireless communication networks. Theoperation may vary in other examples. In this example, 5G communicationnetwork 400 enforces a user policy for a low latency slice type for UE401 and directs 5G communication network 430 to enforce a user policyfor a high throughput slice type for UE 431, however the user policiesmay differ in other examples.

The RRC in UE 401 attaches to the RRC in CU 413 over the PDCPs, RLCs,MACs, and PHYs. The RRC in UE 401 transfers a PLMN ID and SUCI for UE401 to the RRC in CU 413 over the PDCPs, RLCs, MACs, and PHYs. The RRCin CU 413 transfers a registration request for UE 401 that indicates thePLMN ID and SUCI of UE 401 to AMF 421. AMF 421 interacts with othernetwork functions to authenticate and authorize UE 401 for visiting dataservices. AMF 421 determines UE 401 is visiting from other 5Gcommunication network 430 based on the PLMN ID. Responsive to theauthentication and authorization, AMF 421 transfers a context requestfor UE 401 to UDM 424 and indicates UE 401 is visiting from other 5Gcommunication network 430. UDM 424 transfers default UE context per theroaming agreement between networks 400 and 430 to AMF 421. The UEcontext comprises default QoS, default slice IDs, and default networkaddresses. AMF 421 transfers the default UE context for UE 401 to theRRC in CU 413. The RRC in CU 413 transfers the default UE context to theRRC in UE 401 over the PDCPs, RLCs, MACs, and PHYs.

A user application in UE 401 executes and the RRC in UE 401 wirelesslytransfers a PDU session request to the RRC in CU 413 over the PDCPs,RLCs, MACs, and PHYs. The RRC in CU 413 transfers the PDU sessionrequest to AMF 421. AMF 421 queries PCF 425 for policy rules to supportthe requested PDU session requested. PCF 425 directs AF 426 to retrieveservice policies for UE 401 from other 5G communication network 430. AF426 indicates the SUCI for UE 401 and transfers a visiting servicerequest for UE 401 to oAF 456. oAF 456 notifies oPCF 455 of the servicerequest and SUCI for UE 401. oPCF 455 identifies UE 401 based on theSUCI for UE 401 and interacts with oUDM 454 to identify authorizedservices for UE 401. oPCF 455 responsively determines that UE 401 isauthorized for low-latency slice types. oPCF 455 indicates that UE 401is authorized for low-latency slice types to oAF 456.

oAF 456 receives the indication from oPCF 455 and generates a policytemplate for UE 401 that comprises low-latency slice types for UE 401.oAF 456 transfers the policy template for UE 401 to AF 426. AF 426processes the policy template and responsively generates a user policybased on the policy template. The proposed user policy includes alow-latency slice type for UE 401. AF 426 transfers the proposed userpolicy for UE 401 to oPCF 455 over oAF 456. oPCF 455 processes the userpolicy and responsively approves the proposed low-latency slice type forthe user policy for UE 401. oPCF 455 transfers a policy approval to oAF456. oAF 456 transfers the policy approval to AF 426.

In response to the policy approval, AF 426 transfers the user policy forthe low-latency slice type for UE 401 to PCF 425. PCF 425 directs UDM424 to update the UE context for UE 401 to include the low-latency slicetype. PCF 425 approve the PDU session for UE 401 and directs AMF 421 toimplement the user policy for UE 401. In response, AMF 421 retrieves theupdated UE context for UE 401 from UDM 424. AMF 421 transfers theupdated UE context for UE 401 to SMF 422. AMF 421 directs SMF 422 toestablish the PDU session for UE 401 on a low-latency slice. SMF 422selects UPF 423 to serve the PDU session to UE 401 on the low-latencyslice based on the updated UE context. SMF 422 transfers session contextthat indicates UPF 423 to AMF 421. AMF 421 transfers the session contextfor the PDU session to the RRC in CU 413. The RRC in CU 413 transfersthe session context to the RRC in UE 401 over the PDCPs, RLCs, MACs, andPHYs. The RRC in UE 401 directs the SDAP in UE 401 to initiate the PDUsession based on the session context. The SDAP in UE 401 exchanges lowlatency user data for the PDU session with the SDAP in CU 413 over thePDCPs, RLCs, MACs, and PHYs. The SDAP in CU 413 exchanges thelow-latency user data for the PDU session with UPF 423. UPF 423exchanges the low-latency user data for the PDU session with externalnetworks.

AF 426 receives a visiting service request from oAF 456. The visitingservice request indicates the SUCI and a PDU session request for UE 431.AF 426 identifies UE 431 based on the SUCI and transfers the servicerequest to PCF 425. PCF 425 retrieves authorized services for UE 431from UDM 424 and determines that UE 431 is authorized for highthroughput slice types. PCF 425 indicates that UE 401 is authorized forhigh throughput slice types to AF 426. AF 426 responsively generates apolicy template for UE 431 that indicates UE 431 is authorized for highthroughput slice types. AF 426 transfers the policy template for UE 431to oAF 456. oAF 456 processes the policy template and responsivelygenerates a user policy that comprises a high throughput slice type forUE 431. oAF 456 transfers the proposed user policy for UE 431 to PCF 425over AF 426. PCF 425 processes the user policy and responsively approvesthe proposed high-throughput slice type for UE 431. PCF 425 transfers apolicy approval to oAF 456 over AF 426.

In response to the policy approval, oAF 456 transfers the user policyfor UE 431 to oPCF 455. oPCF 455 distributes the user policy for UE 431to oUDM 454 and oAMF 451. oUDM 454 updates the UE context for UE 431 toinclude the high throughput slice type. oPCF 455 approves a highthroughput PDU session for UE 431. In response, oAMF 451 retrieves theupdated UE context for UE 431 from oUDM 454. oAMF 451 directs oSMF 452to establish the PDU session for UE 431 on a high throughput slice. oSMF452 selects oUPF 453 to serve the PDU session to UE 431 on the highthroughput slice. oSMF 452 transfers session context to oAMF 451. oAMF451 transfers the session context for the PDU session to the RRC in CU443. The RRC in CU 443 transfers the session context to the RRC in UE431 over the PDCPs, RLCs, MACs, and PHYs. The RRC UE 431 directs theSDAP in UE 431 to begin the PDU session. The SDAP in UE 431 exchangesuser data for the PDU session with the SDAP in CU 443 over the PDCPs,RLCs, MACs, and PHYs. The SDAP in CU 443 exchanges the user data for thePDU session with oUPF 453. oUPF 453 exchanges the user data for the PDUsession with external networks.

The wireless data network circuitry described above comprises computerhardware and software that form special-purpose network circuitry toenforce a user policy for a UE and to direct another wirelesscommunication network to enforce another user policy for another UE. Thecomputer hardware comprises processing circuitry like CPUs, DSPs, GPUs,transceivers, bus circuitry, and memory. To form these computer hardwarestructures, semiconductors like silicon or germanium are positively andnegatively doped to form transistors. The doping comprises ions likeboron or phosphorus that are embedded within the semiconductor material.The transistors and other electronic structures like capacitors andresistors are arranged and metallically connected within thesemiconductor to form devices like logic circuitry and storageregisters. The logic circuitry and storage registers are arranged toform larger structures like control units, logic units, andRandom-Access Memory (RAM). In turn, the control units, logic units, andRAM are metallically connected to form CPUs, DSPs, GPUs, transceivers,bus circuitry, and memory.

In the computer hardware, the control units drive data between the RAMand the logic units, and the logic units operate on the data. Thecontrol units also drive interactions with external memory like flashdrives, disk drives, and the like. The computer hardware executesmachine-level software to control and move data by driving machine-levelinputs like voltages and currents to the control units, logic units, andRAM. The machine-level software is typically compiled from higher-levelsoftware programs. The higher-level software programs comprise operatingsystems, utilities, user applications, and the like. Both thehigher-level software programs and their compiled machine-level softwareare stored in memory and retrieved for compilation and execution. Onpower-up, the computer hardware automatically executesphysically-embedded machine-level software that drives the compilationand execution of the other computer software components which thenassert control. Due to this automated execution, the presence of thehigher-level software in memory physically changes the structure of thecomputer hardware machines into special-purpose network circuitry toenforce the user policy for the UE and to direct the other wirelesscommunication network to enforce the other user policy for the other UE.

The above description and associated figures teach the best mode of theinvention. The following claims specify the scope of the invention. Notethat some aspects of the best mode may not fall within the scope of theinvention as specified by the claims. Those skilled in the art willappreciate that the features described above can be combined in variousways to form multiple variations of the invention. Thus, the inventionis not limited to the specific embodiments described above, but only bythe following claims and their equivalents.

What is claimed is:
 1. A method of operating a wireless communicationnetwork to deliver policy enforcement to a wireless user device visitingin another wireless communication network, the method comprising:wirelessly serving, by a Policy Control Function (PCF), the wirelessuser device based on home policies for the wireless user device;receiving, by the PCF, a policy request via an Application Function (AF)indicating the wireless user device is visiting a visited wirelessnetwork; in response, accessing, by the PCF, a subscriber profile forthe wireless user device stored by a Unified Data Management (UDM) thatindicates the home policies for the wireless user device; selecting, bythe PCF, one or more of the home policies for the wireless user device;indicating, by the PCF, the selected one or more of the home policies tothe AF; receiving, by the AF, the selected one or more of the homepolicies; generating, by the AF, a policy template that comprises theselected one or more of the home policies; transferring, by the AF, thepolicy template that comprises the selected one or more of the homepolicies for the wireless user device to a visited AF in the visitedwireless network, wherein the visited AF transfers the policy templateto a visited PCF in the visited wireless communication network and thevisited PCF enforces the selected one or more of the home policies forthe wireless user device.
 2. The method of claim 1 wherein selecting, bythe PCF, the one or more of the home policies for the wireless userdevice comprises selecting a slice type for the wireless user device andwherein the visited PCF receives the policy template and enforces theslice type for the wireless user device.
 3. The method of claim 1wherein selecting, by the PCF, the one or more of the home policies forthe wireless user device comprises selecting a Local Breakout (LBO)policy for the wireless user device and wherein the visited PCF receivesthe policy template and enforces the selected LBO policy for thewireless user device.
 4. The method of claim 1 wherein selecting, by thePCF, the one or more of the home policies for the wireless user devicecomprises selecting a Quality-of-Service (QoS) policy for the wirelessuser device and wherein the visited PCF receives the policy template andenforces the selected QoS policy for the wireless user device.
 5. Themethod of claim 1 wherein selecting, by the PCF, the one or more of thehome policies for the wireless user device comprises selecting abit-rate policy for the wireless user device and wherein the visited PCFreceives the policy template and enforces the selected bit-rate policyfor the wireless user device.
 6. The method of claim 1 whereinselecting, by the PCF, the one or more of the home policies for thewireless user device comprises selecting a time-based policy for thewireless user device and wherein the visited PCF receives the policytemplate and enforces the selected time-based policy for the wirelessuser device.
 7. The method of claim 1 wherein selecting, by the PCF, theone or more of the home policies for the wireless user device comprisesselecting a location-based policy for the wireless user device andwherein the visited PCF receives the policy template and enforces theselected location-based policy for the wireless user device.
 8. A methodof operating a wireless communication network to deliver policyenforcement to a wireless user device visiting from another wirelesscommunication network, the method comprising: detecting, by the PCF, thewireless user device is visiting from a home wireless communicationnetwork; transferring, by the PCF, a policy request to an ApplicationFunction (AF) to retrieve service policies for the wireless user devicefrom the home wireless communication network; receiving, by the AF, thepolicy request from the PCF; transferring, by the AF, the policy requestto a home AF in the home wireless communication network wherein the homeAF transfers the policy request to a home PCF in the home wirelesscommunication network and the home PCF accesses a subscriber profile forthe wireless user device stored by a home Unified Data Management (UDM)that indicates home policies for the wireless user device, selects oneor more of the home polices for the wireless user device, and indicatesthe selected one or more of the home policies to the home AF, and thehome AF generates a policy template that comprises the selected one ormore of the home policies and transfers the policy template to the AF;receiving, by the AF, the policy template that comprises the selectedone or more of the home policies from the home AF; generating, by theAF, one or more service policies for the wireless user device based onthe selected one or more of the home policies; transferring, by the AF,the one or more service policies to the PCF; receiving, by the PCF, theone or more service policies; and enforcing, by the PCF, the one or moreservice policies for the wireless user device.
 9. The method of claim 8wherein the selected one or more of the home policies for the wirelessuser device comprises a slice type for the wireless user device andwherein enforcing, by the PCF, the one or more service policiescomprises enforcing the slice type for the wireless user device.
 10. Themethod of claim 8 wherein the selected one or more of the home policiesfor the wireless user device comprises a Local Breakout (LBO) policy forthe wireless user device and wherein enforcing, by the PCF, the one ormore service policies comprises enforcing the selected LBO policy forthe wireless user device.
 11. The method of claim 8 wherein the selectedone or more of the home policies for the wireless user device comprisesa Quality-of-Service (QoS) policy for the wireless user device andwherein enforcing, by the PCF, the one or more service policiescomprises enforcing the selected QoS policy for the wireless userdevice.
 12. The method of claim 8 wherein the selected the one or moreof the home policies for the wireless user device comprises a bit-ratepolicy for the wireless user device and wherein enforcing, by the PCF,the one or more service policies comprises enforcing the selectedbit-rate policy for the wireless user device.
 13. The method of claim 8wherein the selected one or more of the home policies for the wirelessuser device comprises a time-based policy for the wireless user deviceand wherein enforcing, by the PCF, the one or more service policiescomprises enforcing the selected time-based policy for the wireless userdevice.
 14. The method of claim 8 wherein the selected one or more ofthe home policies for the wireless user device comprises alocation-based policy for the wireless user device and whereinenforcing, by the PCF, the one or more service policies comprisesenforcing the selected location-based policy for the wireless userdevice.
 15. A wireless communication network to enforce home policiesfor a wireless user device over a visited wireless communicationnetwork, the wireless communication network comprising: a Policy ControlFunction (PCF) to serve the wireless user device based on the homepolicies for the wireless user device; the PCF to receive a policyrequest via an Application Function (AF) indicating the wireless userdevice is visiting a visited wireless network; the PCF to access asubscriber profile for the wireless user device stored by a Unified DataManagement (UDM) that indicates the home policies for the wireless userdevice and select one or more of the home polices for the wireless userdevice; the PCF to transfer the selected one or more of the homepolicies to the AF; the AF to receive the selected one or more home ofthe policies from the PCF and generate a policy template comprising theselected one or more of the home policies; and the AF to transfer thepolicy template to a visited AF in the visited wireless communicationnetwork, wherein the visited AF transfers the policy template to avisited PCF in the visited wireless communication network and thevisited PCF enforces the selected one or more of the home policies forthe wireless user device based on the policy template.
 16. The wirelesscommunication network of claim 15 wherein the selected one or more ofthe home policies for the wireless user device comprise a slice type.17. The wireless communication network of claim 15 wherein the selectedone or more of the home policies for the wireless user device comprise aLocal Breakout (LBO) policy.
 18. The wireless communication network ofclaim 15 wherein the selected one or more of the home policies for thewireless user device comprise a Quality-of-Service (QoS) policy.
 19. Thewireless communication network of claim 15 wherein the selected one ormore of the home policies for the wireless user device comprise abit-rate policy.
 20. The wireless communication network of claim 15wherein the selected one or more of the home policies for the wirelessuser device comprise at least one of a time-based policy and alocation-based policy.